chore(config): fix stale gittensory prose in wrangler.jsonc comments by JSONbored · Pull Request #6849 · JSONbored/loopover

JSONbored · 2026-07-17T08:15:56Z

Summary

Continues the repo-wide gittensory -> loopover rebrand cleanup sweep. wrangler.jsonc is the live Cloudflare Worker config, so this is deliberately its own small, isolated PR (comment-only, nothing else bundled in).
Five self-referential comments in the vars block still said "gittensory" meaning "this app" (e.g. "drive two OPERATOR surfaces off gittensory's own review-outcome data"), and one described a since-renamed mention-command prefix ("the @gittensory plan command" -- src/github/commands.ts's actual mention regex has matched @loopover for a while now, verified directly). Also fixed one illustrative repo-list example in a comment.
No vars values changed -- verified with npm run cf-typegen:check that worker-configuration.d.ts is still up to date (the generated types only capture binding/var shapes, not comments), and checked that none of the handful of tests referencing "wrangler.jsonc" inspect this file's actual comment prose (they only use the string as a path/guardrail-classification fixture).
Explicitly re-verified and left untouched:
- The unrelated gittensor (Bittensor subnet) naming at a few nearby lines -- a different term entirely, not part of this rebrand.
- The gittensory-native DB source-column literal and its explanatory comment -- a real value compared against historical rows.
- The JSONbored/gittensory entry in LOOPOVER_PUBLIC_STATS_REPOS -- explicitly justified by the adjacent comment (this repo's own pre-rename audit_events rows are still stored under the old full_name).
- The queue-rename and domain-retirement history comments -- accurate past-tense descriptions of things already renamed/retired.

Scope

The PR title follows type(scope): short summary Conventional Commit format.
This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
I linked a currently open issue this PR resolves -- no issue linked: repo-owner-requested maintainer-equivalent cleanup pass, not a contributor fix tied to a filed issue.

Validation

Safety

No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests -- N/A, no such change (comments only).
API/OpenAPI/MCP behavior is updated and tested where needed -- N/A.
UI changes use live API data or real empty/error/loading states -- N/A.
Visible UI changes include a UI Evidence section -- N/A, no visible change.
Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs (none touched here).

Notes

Third in a small series of PRs sweeping the remaining gittensory references left over from the rebrand (docs(selfhost): fix stale gittensory-selfhost self-host doc defaults #6826 self-hosting docs, chore(config): fix stale gittensory prose in infra/root config files #6841 root/infra config). This is deliberately the smallest, most isolated one given the file's stakes.

Five self-referential comments in wrangler.jsonc's vars block still said "gittensory" where they mean "this app" (e.g. "drive two OPERATOR surfaces off gittensory's own review-outcome data") or described a since-renamed command prefix ("the `@gittensory plan` command" -- the real mention prefix regex in src/github/commands.ts has matched `@loopover` for a while now). Also fixes one illustrative repo-list example. Comment-only change -- verified `npm run cf-typegen:check` still reports worker-configuration.d.ts up to date (no vars/binding shape changed), and none of the handful of tests that reference "wrangler.jsonc" as a path string inspect this file's actual comment prose. Leaves untouched, and re-verified against source before doing so: - The unrelated `gittensor` (Bittensor subnet) naming at lines 32-34, 159-166 -- a different term entirely, not part of this rebrand. - The `gittensory-native` DB source-column literal and its explanatory comment (lines 186-187) -- a real, compared-against-historical-rows value. - The JSONbored/gittensory entry in LOOPOVER_PUBLIC_STATS_REPOS (lines 209, 211) -- explicitly justified by the adjacent comment as needed for this repo's own pre-rename audit_events rows, still stored under the old full_name. - The queue-rename and domain-retirement history comments (lines 41, 286-290) -- accurate past-tense descriptions of things already renamed or retired.

superagent-security · 2026-07-17T08:16:20Z

Superagent didn't find any vulnerabilities or security issues in this PR.

codecov · 2026-07-17T08:21:01Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.63%. Comparing base (d45d8fd) to head (b7d3553).
⚠️ Report is 5 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6849   +/-   ##
=======================================
  Coverage   93.63%   93.63%           
=======================================
  Files         683      683           
  Lines       68163    68163           
  Branches    18706    18706           
=======================================
  Hits        63827    63827           
  Misses       3350     3350           
  Partials      986      986

Flag	Coverage Δ
shard-1	`43.23% <ø> (-0.46%)`	⬇️
shard-2	`36.99% <ø> (+0.25%)`	⬆️
shard-3	`32.64% <ø> (-0.12%)`	⬇️
shard-4	`34.41% <ø> (+0.19%)`	⬆️
shard-5	`31.46% <ø> (-0.90%)`	⬇️
shard-6	`45.87% <ø> (+0.41%)`	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

loopover-orb · 2026-07-17T08:23:08Z

Warning

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-17 08:23:27 UTC}

1 file · 1 AI reviewer · 1 blocker · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
This is a pure comment-string rebrand PR in wrangler.jsonc, replacing five stale self-referential 'gittensory' mentions with 'loopover' and updating one illustrative repo-list example and a mention-command prefix comment. No JSON values, keys, or config semantics change, and CI passed on the exact commit. The diff is well-scoped, matches its stated intent exactly, and correctly leaves untouched the unrelated `gittensor` (Bittensor) naming, the `gittensory-native` DB literal, and the intentionally-preserved `JSONbored/gittensory` stats-repo entry.

Nits — 2 non-blocking

No externally-authorized issue link is cited in the PR description for this rebrand-sweep chore, per repo policy that contributor PRs should close/link an eligible open issue.
Consider a single repo-wide grep/lint pass (or a CI check) for stray 'gittensory' occurrences so future rebrand cleanup doesn't have to be done file-by-file in separate PRs.

Concerns raised — review before merging

No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.

📋 Copy for AI agents — paste into your coding agent

Fix the following blocker(s) from this PR review:

1. No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.

Decision drivers

❌ Code review — 1 blocker (1 reviewer)
❌ Gate result — Blocking (Repo-configured hard blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ No-issue rationale	PR body explains why no issue is linked.
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 33 registered-repo PR(s), 26 merged, 332 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 33 PR(s), 332 issue(s).
Improvement	ℹ️ Insufficient signal	risk: clean · value: insufficient-signal · LLM: minor

Review context

Author: JSONbored
Role context: owner (maintainer lane)
Public audience mode: oss maintainer
Lane context: Repository is configured for direct PR review.
Public profile languages: Python, TypeScript, Ruby, Go, JavaScript, MDX, Shell, Solidity
Official Gittensor activity: 33 PR(s), 332 issue(s).
PR-specific overlap: none found.

Contributor next steps

Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.

Signal definitions

Related work = same linked issue, overlapping active PRs, or title/path similarity.
Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

@loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
@loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

Re-run LoopOver review

loopover-orb Bot added the gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier. label Jul 17, 2026

loopover-orb Bot assigned JSONbored Jul 17, 2026

loopover-orb Bot added the manual-review Gittensor contributor context label Jul 17, 2026

JSONbored merged commit 48a7723 into main Jul 17, 2026
17 checks passed

JSONbored deleted the chore/rebrand-wrangler-comments branch July 17, 2026 08:24

This was referenced Jul 17, 2026

docs(miner): fix stale gittensory prose and broken links in loopover-miner docs #6859

Merged

docs(packages): fix stale gittensory prose and audit citations #6863

Merged

test(services): fix stale actor/repo-key assertions left by the rebrand #6868

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(config): fix stale gittensory prose in wrangler.jsonc comments#6849

chore(config): fix stale gittensory prose in wrangler.jsonc comments#6849
JSONbored merged 1 commit into
mainfrom
chore/rebrand-wrangler-comments

JSONbored commented Jul 17, 2026

Uh oh!

superagent-security Bot commented Jul 17, 2026

Uh oh!

codecov Bot commented Jul 17, 2026 •

edited

Loading

Uh oh!

loopover-orb Bot commented Jul 17, 2026 •

edited

Loading

⏸️ LoopOver review result - manual review recommended

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

JSONbored commented Jul 17, 2026

Summary

Scope

Validation

Safety

Notes

Uh oh!

superagent-security Bot commented Jul 17, 2026

Uh oh!

codecov Bot commented Jul 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

loopover-orb Bot commented Jul 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⏸️ LoopOver review result - manual review recommended

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

codecov Bot commented Jul 17, 2026 •

edited

Loading

loopover-orb Bot commented Jul 17, 2026 •

edited

Loading